home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Precision Software Appli…tions Silver Collection 4
/
Precision Software Applications Silver Collection Volume 4 (1993).iso
/
database
/
pdt_set1.exe
/
PDT-SET1.DOC
< prev
next >
Wrap
Text File
|
1992-06-22
|
89KB
|
1,920 lines
███████┐▐████████┐ ████████┐
██┌──██│ └██┌──██│ └──██┌──┘
███████│ ██│ ██│ ██│
██┌────┘ ██│ ██│ ██│
██│ ▐████████│ ██│
└─┘ └───────┘ └─┘
████████┐ ███████┐ ███████┐ ██┐ ██┐ ███┐ ████┐ ████████┐
└──██┌──┘ ██┌──██│ ██┌──██│ ██│ ██│ ██┌┘ └██┌┘ └──██┌──┘
██│ ██│ ██│ ██│ ██│ ██│ ███████┐ ██│ ██│
██│ ██│ ██│ ██│ ██│ ██│ ██┌──██│ ██│ ██│
██│ ███████│ ███████│ ██████┐ ██│ ██│ ████┐ ██│
└─┘ └──────┘ └──────┘ └─────┘ └─┘ └─┘ └───┘ └─┘
Set #1 Version 1.4 (6/92)
┌────────────────────────── Set #1 ───────────────────────────┐
│ │▄
│ Set #1 includes FIELDS.Exe, CREATE.Exe and DBF-DBF.Exe -- │█
│ programs to document, create, modify, or update dBase files.│█
│ │█
│ As we'll explain later, PDT's Tool Kit contains many things │█
│ to help you create, convert and manage data files. Some │█
│ programs are offered in "shareware versions" as "sets." │█
└─────────────────────────────────────────────────────────────┘█
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Overview
────────
The PDT Tool Kit includes several things to help you manage,
edit, convert and repair data files -- dBase files, or fixed-
length files created by other programs. Uses include:
* Quickly create dBase files with any field structure. Help
you create "dictionaries" of field names to serve as a per-
manent reminder of what fields in dBase files are for.
* Create "sub-sets" of (or modify) dBase files. YOU specify
which fields to include. You can delete fields, add fields,
change field: lengths, types, number of decimal places, etc.
* Quickly convert dBase files to comma-delimited ASCII files.
Or, do the opposite: read ASCII files and save the data
to dBase files. These small, fast programs simplify sharing
data between different programs.
* Review, understand or repair dBase files.
Copyright 1992, Rob W. Smetana, All Rights Reserved
PDT, Pro~Formance Data Tool, PDT Tool Kit, P~F, and
Pro~Formance are Trademarks of Rob W. Smetana.
2
┌────────────────── Using Translate.Exe ────────────────────┐
│ │▄
│ As you can see, this manual contains lines, boxes, shad- │█
│ ing and other "high ASCII" characters. Some printers │█
│ can't print these -- they'll print either nothing, or │█
│ they'll print italic or other characters instead of lines. │█
│ │█
│ If your printer CAN'T print the lines and boxes you see │█
│ here, run Translate.Exe that we included. Run it this way: │█
│ │█
│ translate pdt-set1.doc ???? <enter> │█
│ │█
│ where "????" is either: │█
│ │█
│ - the name of a file (to send translated output to) │█
│ - or LPT1, LPT2 or LPT3 (to tell Translate to print │█
│ pdt-set1.doc). │█
│ │█
│ Translate converts lines, boxes and shading into charac- │█
│ ters ANY printer can handle. For example: │█
│ │█
│ ┌────────┐ +--------+ │█
│ │This Box│ will become |This Box| │█
│ └────────┘ +--------+ │█
│ │█
│ If you tell Translate to print "to a file," you can then │█
│ browse or examine that file. Later, print it by typing: │█
│ │█
│ copy filename LPT1 <enter> (use LPT1, LPT2, LPT3 or PRN) │█
│ │█
│ │█
│ NOTE: Use Translate with ANY text file -- not just this │█
│ file. It comes in very handy when you receive text files │█
│ from authors who provide no way to remove or replace the │█
│ characters in files that your printer CAN'T print. │█
│ │█
└─────────────────────────────────────────────────────────────┘█
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Conventions We Use in this Manual
─────────────────────────────────
"dBase" refers to dBase III, IV or later (not dBase II).
"<cr>" means you should press Enter or Return.
"Esc" means you should press Escape.
"F2" means you should press Function Key F2.
"Ctrl-A" or "Ctrl-D" means you should HOLD DOWN the Ctrl key
and tap A or D.
───────────────────────────────────────────────────────────────
Contents
───────────────────────────────────────────────────────────────
SECTION I: Introduction
Introduction .................................. 4
Getting Tool Kit Utilities; Shareware Versions 4
System Requirements; License ................. 5
To Register ................................... 6
Disclaimer and Limited Warranty ............... 7
Distributing This Software .................... 7
SECTION II: Using the Tool Kit's Programs ........ 8
General Syntax ................................ 9
Using FIELDS ............................... 10
Using CREATE ............................... 11
Using DBF-DBF ............................... 15
Using DBF-ASC \ These are part of Set #2. They
Using ASC-DBF / are discussed in their own manual.
SECTION III: Creating Definition Files ............ 19
SECTION IV: Error Message ........................ 22
SECTION V: Using the FIX-DBF Structure Files .... 24
Using FIX-DBF.HDR \ PDT's Registered users receive
Using FIX-DBF.FLD / these to help them understand
and repair dBase files.
APPENDIX I: A Summary of our Many Programs ....... 25
APPENDIX II: Order Form ........................... 36
4
───────────────────────────────────────────────────────────────
SECTION I: Introduction
───────────────────────────────────────────────────────────────
The PDT Tool Kit is a companion to PDT (the Pro~Formance Data
Tool). PDT is a phenomenal program to view, edit and manage
ANY file -- up to 2 gigabytes in size. And PDT offers special
features that makes viewing and editing dBase (or other fixed-
length database) files a snap! With PDT you can view and edit:
data files, binary files (fonts, executable programs), EBCDIC
or ASCII files -- ANY file of virtually ANY size!
PDT's Tool Kit includes several things to help you manage,
edit, convert and repair data files -- dBase files, or fixed-
length or ASCII files created by other programs.
First, the Tool Kit offers several, small, fast programs to
help you Create or Modify dBase files, or Convert data files
from one format (eg., dBase) to another (eg., ASCII).
Second, the Tool Kit also contains files to help you fix ANY
dBase file (or to simply explore the structure of dBase files).
These "structure files" may be used with our PDT program to open
dBase files, examine the dBase "header" or "field structure,"
and then, if necessary, edit things to fix corrupted dBase files.
Availability; "Shareware" Versions
──────────────────────────────────
The complete PDT Tool Kit is FREE to PDT's registered users.
The PROGRAMS in the Tool Kit are also available separately as
"user-supported" programs. "Shareware" versions work much like
the registered versions. The only differences MAY be that:
* Registered users receive the latest versions which usually
have added features, greater capacity, etc. For example,
we're adding features right now that'll let you "justify"
fields -- something that can be critical with fields like
phone numbers or ZIP/MAIL codes, and "nice-to-have" with
other types of fields. Registered versions handle up to
255 fields, versus early versions designed to handle 25.
* The entire PDT Tool Kit is sent FREE to PDT's registered
users. Shareware versions are available separately -- in
sets which consist of 1 or more related programs. For
example, DBF-ASC and ASC-DBF let you convert files back
and forth between dBase and comma-delimited ASCII formats.
Users of shareware versions can register for each "set" of
tools separately. Or they can register for the entire Tool
Kit -- and get latest versions of everything, PLUS any new
programs we've added!
System Requirements 5
───────────────────────────────────────────────────────────────
These programs run on IBM XTs, ATs, PS/2s and strict
compatibles running DOS 2.1 or later.
Monitor: Any
Memory: About 128k
Disk Drives: Hard disk recommended; floppy disks are fine
Printer: Any. We don't use your printer.
License
───────────────────────────────────────────────────────────────
These programs are NOT free software. They're neither "public
domain" software nor "freeware." They are "user-supported"
software.
This software is Copyright 1987-1992, Rob W. Smetana. It is
protected by both United States copyright law and inter-
national treaty provisions. All Rights Reserved Worldwide.
REGISTERED VERSIONS
───────────────────
Registered users must treat this software like a copyrighted
book. You may use it on any number of computers/CPUs, pro-
vided there is NO POSSIBILITY that it will be running on two
or more computers at the same time.
You may make a "backup" copy of this software for the sole
purpose of guarding against the loss of this software and
protecting your investment.
SHAREWARE VERSIONS
──────────────────
You may try out shareware (or "user-supported") versions to
determine if they satisfies your needs. After using shareware
versions beyond the trial period (30 days or 20-25 sessions),
you MUST register to continue using it -- or stop using it.
This is NOT free software. The next page explains the benefits
of registering and how to register.
* This is copyrighted software that's distributed through both
retail and shareware channels. Shareware versions let you
try it out before buying it.
* If you paid a "shareware distributor" a $2-$6 fee for a
disk that contained this program:
- You paid them for copying the disk and sending it to you.
- You did NOT pay for the software. NONE of the fees you
pay shareware distributors go to the authors of shareware
programs. If you use these programs, you must pay for them.
To Register 6
───────────────────────────────────────────────────────────────
When you register, we "say thanks" in many ways.
* First, we send you the latest versions of these programs,
which usually have new or enhanced features. For example,
we're now adding several new features: options to "justify"
fields (right or left), greater capacity (250 fields versus
25 fields), etc..
* Second, if you order the complete Tool Kit, we'll also
include any new programs we've added since we wrote this.
We'll also include the "FIX_DBF" files you can use with
PDT to fix, repair, or simply examine dBase files.
To Register
───────────
You may register in several different ways:
1. CALL (415) 863-0530 with your VISA or MasterCard number.
This is the fastest way to register. It often cuts 2-3
weeks off the turn-around time -- since you needn't wait
for your order to reach us and your check to clear the bank.
2. To register by mail:
- Complete the order form at the end of this manual.
- Or send your registration fee plus $4 shipping &
handling ($8 shipping outside the U.S. and Canada),
along with your name, address and phone number to:
Pro~Formance (415) 863 - 0530
Rob W. Smetana
132 Alpine Terrace
San Francisco, Ca 94117
DISCLAIMER and WARRANTY 7
───────────────────────────────────────────────────────────────
Pro~Formance and Rob W. Smetana make no representations or
warranties with respect to the contents or use of this manual
and/or the Pro~Formance Data Tool (PDT) or PDT's Tool Kit.
We specifically disclaim any express or implied warranties of
merchantability or fitness for any particular purpose.
We reserve the right to revise this manual and/or the programs
described herein and to make changes to their operation inter-
face or functionality, at any time, without notice and without
obligation to notify any person or entity of such changes or
revisions.
DISTRIBUTING THIS SOFTWARE
───────────────────────────────────────────────────────────────
Shareware distributors, bulletin boards and user clubs may
distribute "user-supported" (or shareware) versions of this
software provided that:
* Your company name, literature, etc. do not promote or
include the words "freeware" or "free" software -- which
terms misrepresent "user-supported" software. Expressly
prohibited from distributing any software by Pro~Formance,
Rob W. Smetana and/or Brandon S. Smetana are: American
Freeware, California Freeware and U.S. Freeware.
* Your firm or organization does not include among it's
owners, employees, members or associates Ronald Chordigian
or any member of his family.
* You include, unmodified, all files included with this
software including:
PDT-Set1.Doc, Create.Exe, DBF-DBF.Exe, and any other files
mentioned in Readme.Bat or Packing.Lst.
* You charge a "distribution fee" of no more than $8 (US).
* You clearly state that continued use of "user-supported"
software REQUIRES paying for the software.
8
───────────────────────────────────────────────────────────────
SECTION II: Using the Tool Kit Programs
───────────────────────────────────────────────────────────────
Here's a summary of each program in PDT's Tool Kit. The number
beside each program name indicates which "set" it's in.
Set Program Description
─── ─────────── ───────────────────────────────────────────────
ALL Fields.Exe Reads field definitions from a dBase file and
saves them to another file. Edit this 2nd
file to create a handy "dictionary" or record
of what's in dBase files, and what the
purpose of each field is.
1 Create.Exe Create dBase database files -- with any
structure you like!
1 DBF-DBF.Exe Modify the structure of existing dBase files.
You may delete fields, add fields, change the
width of fields, etc. Or, create new dBase
files with field structures and data you prefer.
2 DBF-ASC.Exe DBF-ASC.Exe reads dBase files and creates
2 ASC-DBF.Exe comma-delimited ASCII files. ASC-DBF.Exe
does the opposite: it reads comma-delimited
ASCII files and saves dBase files.
NOTE: DBF-ASC lets you save "definition
files" allowing you to easily and quickly go
back and forth between dBase and ASCII files.
These also serve as useful records of the
structure of hard-to-read ASCII files!
General Syntax 9
══════════════
In general, you'll run each program something like this:
ProgramName file_1 file_2 file_3 <enter>
In other words, at the DOS prompt, type the Program Name
followed by 1 - 3 file names. File names will be files:
* That you want to create.
* That you want to read.
* Or that contain information that defines the structure of
data files. (Called "Definition Files." we'll explain
these later.)
NOTE: For each program, you must send it 1-3 file names. As
we explain how to use each program, we'll explain what
that program needs.
If you can't recall how to run a program, at the DOS
prompt just type: ProgramName <enter>
The program will beep and display the syntax you should
use to run it.
ALSO
NOTE: Some programs need "definition files."
* These are simple ASCII files you can create with
any editor or word processor.
* They define the "fields" in data files: the name of
each field, how wide it is, and what "type" of field
it is (ie., Character, Numeric, Date, etc.)
When we discuss each program, if a definition file is
needed, we'll explain the format to use. See SECTION
III: Definition Files used by Tool Kit Programs, for
specific details on creating these files.
Using Fields 10
───────────────────────────────────────────────────────────────
Name: Fields.Exe.
Purpose: * When you create a database file, you have a clear
idea of what each field in the data file is for.
But suppose you get promoted and someone else is
assigned to manage that data file! They may have
no idea what each field is for -- especially when
field names are a terse 1-10 characters long as
they are in dBase files.
* Fields.Exe helps you create a record (dictionary)
of what a database file is for, which fields are
in it, and what the purpose of each field is.
* Fields will read the field definitions from a
dBase file and save them to another file (a
".!!!" file). YOU should then edit this 2nd
file. Beside each field name, add a description
of what that field is used for.
NOTE: Whenever you use Create.Exe, we urge you to immedi-
ately run Fields on the dBase file you just created!
Syntax: fields dbase.dbf <enter>
Replace "dbase.dbf" with the name of the dBase
file you want to read Be sure to specify a
drive/directory if your dBase file is elsewhere.
If we can't find "dbase.dbf" we'll print an error
message and end.
If a file already exists called "dbase.!!!", we'll
end, telling you to rename or delete it first.
Requires: Nothing.
Running Type: fields dbase.dbf <enter>
Fields:
Fields will quickly read the "header" of the dBase
file and save the "field definitions" in a file
called "dbase.!!!" -- with the same name as your
dBase file, but with a ".!!!" extension. We'll
save "dbase.!!!" on the same drive/directory as
"dbase.dbf.
Now EDIT dbase.!!! and, beside each field, enter a
description of what that field is for. When you're
done, print the file: copy dbase.!!! prn <enter>.
That's it! Fields is small and very fast.
Using Create 11
───────────────────────────────────────────────────────────────
Name: Create.Exe.
Purpose: * To create (or initialize) a new dBase file with
just the dBase HEADER. Other programs (like PDT,
inform-Z, dBase, FOX Pro, etc.) read that header
to determine the "field structure" of that file.
* The file will be empty -- it'll have 0 records.
To add data (or blank records) to it:
- Run PDT and open the file (ctrl-O).
- Turn edit ON, then press Insert to add some
blank space. Insert, for example, 10-100
blank records (which takes less than a second).
Then edit records as you like.
Syntax: create dbase.fil [optional: definition.fil] <enter>
If you specify a definition file, we'll load it
and display the field names so you can edit them.
Press F2 to save your dBase file, or ESCAPE to quit.
Optional: A "definition file" indicating the:
- Names of fields to add to the dBase file.
- Width of each field (1 to 254 characters).
- Type of field each is (see below for details).
SECTION II explains how to create Definition Files.
Basically they look like this:
Instructions to you (required) Line 1
" " " " Line 2
" " " " Line 3
" " " " Line 4
Width , Type , Name Line 5 +
In other words, we skip lines 1-4 (but you MUST
include them). Beginning on line #5, add one
line for each field in the dBase file. For each
field you MUST include 3 pieces of information,
separated by 2 (and ONLY 2) commas.
Example: 25 , C , First_Name
This creates a Character field ("C") that'll be
25 spaces wide and we'll call it "First_Name."
continued . . .
Using Create (continued) 12
dBase dBase places restrictions on field names, types
Limitations: and widths. SECTION II has details. Briefly:
Field NAMES: 10 characters maximum. They should
begin with A-Z, and may contain A-Z,
0-9 and "_" (the underscore). Names
WILL be capitalized, but you may
enter them in upper or lower case.
Field TYPE Field types include C, N, D, L and M.
and WIDTH: The width of some field types is fixed:
Symbol Type Width
══════ ═════════ ═══════
C Character 1 - 254
D Date 8
M Memo 10
L Logical 1
N Numeric 1 - 15
Other
Limitations: None.
Running create dbase.fil [optional: definition.fil] <enter>
Create:
Definition files make it easy to create the same
(or similar) dBase files over and over. Once we
load and display field names, just edit them to
your liking. If you do NOT specify a definition
file, we'll begin with field #1. Enter as many
fields as you like.
Replace "definition.fil" with the name of your
definition file, and "dbase.dbf" with the name of
the dBase file you want to create.
Be sure to specify a drive/directory if:
- Your definition file is elsewhere.
- Or, you want Create to save your dBase file
to a path other than the one you're on.
If Create can't find "definition.fil" it'll
print an error message and end.
If a file already exists called "dbase.dbf", we'll
ask if you want to Overwrite it or Quit.
continued . . .
Using Create (continued) 13
When you run Create, you'll work in a screen like this.
█▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█
█ Field # Decimal ┬ █
█ # Field Name Type Width Places │ Esc = Cancel █
█───────────────────────────────────────┤ F2 = Save █
█ 1 First_Name C 15 0 │ █
█ 2 Last_Name C 15 0 │ ctrl-A = Add Field █
█ 3 Address C 20 0 │ ctrl-D = Delete " █
█ 4 City C 20 0 │ █
█ 5 State C 2 0 │ Tab/CR = Move Right█
█ 6 Zip_Code C 10 │Shft-Tab = Move Left █
█ ├─────────────────────█
█ ^ │# Fields = 6 █
█ │ │Rec. Len = 82 █
█─────────────┼─────────────────────────┴─────────────────────█
█ │ █
█▄▄▄▄▄▄▄▄▄▄▄▄▄│▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█
│
│
The main body ┘ lists the field names, types and widths. Edit
any field, and add or delete fields.
Press: To:
───────── ─────────────────────────────────────────────────
F2 Save your dBase file with the structure you see.
Esc Quit -- either to cancel the action, or to exit
the program after you save your dBase file.
Up/Down Move up or down to highlight a field you want to
PgUp/PgDn review or edit.
Ctrl-Home/ Move to the top or bottom of the list.
Ctrl-End
Tab/Enter Move right on a line.
Shift-Tab Move left on a line.
Ctrl-A Add/Insert a field at the line that's highlighted.
Ctrl-D Delete the field that's highlighted.
Ctrl-Home Erase the contents of a field.
Ctrl-End Delete from the cursor to the end of the field.
Alt-U UnDo the last edit. For example, if, by mistake
you pressed Ctrl-Home and erased the name of a
field, press Alt-U to restore the original.
NOTE: Alt-U will undo ONLY editing changes. It
will NOT restore fields you delete with ctrl-D!
continued . . .
Using Create (continued) 14
As you move left or right to edit Field Names, Width, Type
or Decimal Places, we'll display a message near the bottom
of your screen indicating what you should enter there.
We'll also display error messages there if you enter something
that's "illegal" -- like a field type that dBase won't allow.
Note that you can edit # of Decimal Places ONLY for dBase
Numeric fields (ie., there's an "N" under "Type"). Decimal
Places are irrelevant for other types of dBase fields.
Errors That Might Occur When Using Create
─────────────────────────────────────────
* Field Names: While editing (and before you press F2)
we'll check to see if the field name is blank (which
would be illegal in a dBase file).
But we WON'T check the strict validity of field names until
you press F2 to save your dBase file. At that point, two
errors may occur:
- A field name is ILLEGAL: it contains other than A-Z, 0-9
and the underscore "_".
- A field name ALREADY EXISTS: duplicate names are illegal.
If these errors occur, we'll tell you the number of the
field where the error occurred, and show you the error num-
ber. Edit a name, or check for duplicates, then try again.
* If other types of errors occur, we'll normally display
an error number. Consult SECTION IV to determine why the
error occurred. Try to fix the error, then try saving again.
Using DBF-DBF 15
───────────────────────────────────────────────────────────────
Name: DBF-DBF.Exe.
Purpose: * Modify the structure of dBase files. Add fields,
delete fields, change the width or type of fields.
* Or create new dBase files with at least some of
the information from existing dBase files.
* Unlike Create.Exe, which creates dBase files
with only the header, DBF-DBF creates new dBase
files with BOTH the header AND data.
NOTE: DBF-DBF does NOT modify existing dBase files.
Instead, it reads one dBase file and creates a 2nd
one based on the modified structure of the 1st one.
ALSO NOTE: PDT has several options that let you
modify the structure of dBase files. For example,
you can Expand or Shrink the width of fields.
But PDT will NOT let you delete fields -- because
that's such a drastic operation. DBF-DBF won't
either. But it WILL let you create another version
of a dBase file, deleting some original fields.
Syntax: dbf-dbf dbase_1.dbf dbase_2.dbf <enter>
"dbase_1.dbf" is the name of an existing dBase
file. "dbase_2.dbf" is the name of the dBase file
you want to create.
If we can't find dbase_1.dbf, we'll tell you so
and end. If dbase_2.dbf exists, we'll ask if you
want to Overwrite it or Quit. We won't ADD to
existing dBase files; we'll just create them. But
note that it's v-e-r-y easy to use PDT to copy
records from one file to another!
DBF-DBF will read the field structure of the 1st
dBase file, then let you edit, add or delete fields.
Press F2 to save dbase_2.dbf, or ESCAPE to quit.
continued . . .
Using DBF-DBF (continued) 16
Requires: Free disk space equal to the size of dbase_1.dbf.
NOTE: This may or may not be enough, depending on
how many fields you add to dbase_1.dbf, and how
wide these new fields are. As a safety precaution,
we urge you to run DBF-DBF only when available disk
space equals 3 TIMES the size of dbase_1.dbf.
Definition files are NOT required since we read the
database structure from dbase_1.dbf.
dBase dBase places restrictions on field names, types
Limitations: and widths. SECTION III has details. Briefly:
Field NAMES: 10 characters maximum. They should
begin with A-Z, and may contain A-Z,
0-9 and "_" (the underscore). Names
WILL be capitalized, but you may
enter them in upper or lower case.
Field TYPE Field types include C, N, D, L and M.
and WIDTH: The width of some field types is fixed:
Symbol Type Width
══════ ═════════ ═══════
C Character 1 - 254
D Date 8
M Memo 10
L Logical 1
N Numeric 1 - 15
Running dbf-dbf dbase_1.dbf dbase_2.dbf <enter>
DBF-DBF:
Replace "dbase_1.dbf" with the name of an existing
dBase file, and "dbase_2.dbf" with the name of
the dBase file you want to create.
Be sure to specify a drive/directory if:
- dbase_1.dbf is elsewhere.
- Or, you want to create dbase_2.dbf on a drive/
directory other than the one you're on.
If we can't find "definition.fil" we'll print an
error message and end.
If a file already exists called "dbase.dbf", we'll
ask if you want to Overwrite it or Quit.
continued . . .
Using DBF-DBF (continued) 17
When DBF-DBF runs, it reads the field definitions of the 1st
dBase file you mentioned, then displays a screen like this:
█▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█
█ Field # Decimal ┬ █
█ # Field Name Type Width Places │ Esc = Cancel █
█───────────────────────────────────────┤ F2 = Save █
█ 1 First_Name C 15 0 │ █
█ 2 Last_Name C 15 0 │ ctrl-A = Add Field █
█ 3 Address C 20 0 │ ctrl-D = Delete " █
█ 4 City C 20 0 │ █
█ 5 State C 2 0 │ Tab/CR = Move Right█
█ 6 Zip_Code C 10 │Shft-Tab = Move Left █
█ ├─────────────────────█
█ ^ │# Fields = 6 █
█ │ │Rec. Len = 82 █
█─────────────┼─────────────────────────┴─────────────────────█
█ │ █
█▄▄▄▄▄▄▄▄▄▄▄▄▄│▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█
│
└───┐
In the main body ─┘ edit any field, or add or delete fields.
Press: To:
───────── ─────────────────────────────────────────────────
F2 Save your dBase file with the structure you see.
Esc Quit -- either to cancel the action, or to exit
the program after you've saved your dBase file.
Up/Down Move up or down to highlight a field you want to
PgUp/PgDn review or edit.
Ctrl-Home/ Move to the top or bottom of the list.
Ctrl-End
Tab/Enter Move right on a line.
Shift-Tab Move left on a line.
Ctrl-A Add/Insert a field at the line that's highlighted.
Ctrl-D Delete the field that's highlighted.
Ctrl-Home Erase the contents of a field.
Ctrl-End Delete from the cursor to the end of the field.
Alt-U UnDo the last edit. For example, if, by mistake
you pressed Ctrl-Home and erased the name of a
field, press Alt-U to restore the original.
NOTE: Alt-U will undo ONLY editing changes. It
will NOT restore fields you delete with ctrl-D!
continued . . .
Using DBF-DBF (continued) 18
As you move left or right to edit Field Names, Width, Type
or Decimal Places, we'll display a message near the bottom
of your screen indicating what you should enter there.
We'll also display error messages there if you enter something
that's "illegal" -- like a field type that dBase won't allow.
Note that you can edit # of Decimal Places ONLY for dBase
Numeric fields (ie., there's an "N" under "Type"). Decimal
Places are irrelevant for other types of dBase fields.
Errors That Might Occur
───────────────────────
* Field Names: While editing (and before you press F2) we
will check to see if the field name is blank (which would
be illegal in a dBase file).
But we WON'T check the strict validity of field names until
you press F2 to save your dBase file. At that point, two
errors may occur:
- A field name is ILLEGAL: it contains other than A-Z, 0-9
and the underscore "_".
- A field name ALREADY EXISTS: duplicate names are illegal.
If this type of error occurs, we'll tell you the number of
the field where the error occurred, and show you the error
number. Edit a name, or check for duplicates, then try again.
* If other types of errors occur, we'll normally display
an error number. Consult SECTION IV to determine why the
error occurred. Try to fix the error, then try saving again.
19
───────────────────────────────────────────────────────────────
SECTION III: Creating Definition Files
───────────────────────────────────────────────────────────────
"Definition Files" are used by several of the programs in PDT's
Tool Kit. You can create them with any editor or word processor.
They must be saved in ASCII (or DOS text) format. That means:
* They must have no formatting codes like the ones word pro-
cessors use to symbolize font changes, line spacing, etc.
* Each line must end with a carriage return/line feed.
Both of these conditions are usually met if you use your word
processor's ASCII or DOS text option to save the files.
┌───────────────────────────── NOTE ─────────────────────────────┐
│ │▄
│ If you've used PDT, you're probably familiar with PDT's │█
│ "structure files." Definition files resemble structure │█
│ files -- but there are some v-e-r-y important differences: │█
│ │█
│ Definition Files Structure Files │█
│ ──────────────── ─────────────── │█
│ * Lines 1-4 Ignored (instructions) Used │█
│ │█
│ * 1st entry of │█
│ Field Def: Field WIDTH (or -1) Field START │█
└────────────────────────────────────────────────────────────────┘█
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Definition Files have the following basic format:
Instructions to you (required)
" " " "
" " " "
" " " "
Width , Type , Name
Lines 1-4 contain instructions to you. They may contain
ANYTHING (they can even be blank). But they must be there.
Beginning on line #5, add 1 line for each field.
* Each line must have 3 sections separated by 2 (and ONLY
2 commas): Field Width, Field Type, Field Name.
this is VALID: 22 , C , First_Name
this is INVALID: 1,200 , C , Memo_Data
In the 2nd, invalid example, there are 3 commas. The
error is in "1,200." It should read: 1200, C, Memo_Data.
* "22, C, First_Name" describes a "C" (Character) field 22
characters wide named "First_Name."
Field Types 20
───────────
Here are the symbols you'd enter to indicate field TYPES.
══════ dBase Field Types ═════ ═══ Non-dBase Field Types ════
Use This For This Field Use This For This Field
Symbol Type of Field Width Symbol Type of Field Width
──────── ───────────── ───── ──────── ───────────── ─────
C Character 1-254 c Character ?
N Numeric 1-15 t Tiny Integer 1
L Logical 1 i Integer 2
M Memo 10 l Long Integer 4
D Date 8 s Single MS 4
j Single IEEE 4
d Double MS 8
k Double IEEE 8
$ Currency 8
┌─────────────────────── TIPS & NOTES ────────────────────────┐
│ │▄
│ Note that symbols for dBase files are UPPER case, while │█
│ symbols for non-Dbase field types are all in lower case. │█
│ │█
│ In the non-dBase list, note the s/j and d/k pairs -- indi- │█
│ cating Microsoft (MS) versus IEEE formats, respectively. │█
└─────────────────────────────────────────────────────────────┘█
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Field Widths
────────────
Depending on the field TYPE, the width of the field may be
fixed or variable.
The column "Field Width" indicates how many characters/columns
each field was allocated. Notice that Character fields (and
dBase Numeric fields) are "?" wide -- they vary in width. But
other fields have fixed widths.
An easy way to determine the width of fields is to load a file
into PDT, put your cursor on the 1st character of a field, press
ctrl-B (begin marking a block), move the cursor right to the end
of the field, then note the number PDT shows you in the lower
left corner of the file window: "BLK: ###."
┌─────────────────────── REMEMBER: : : ───────────────────────┐
│ │▄
│ When creating definition files to read comma-delimited │█
│ ASCII files, use a field width of "-1" to indicate fields │█
│ we should skip. NEVER just ignore the field! │█
│ │█
└─────────────────────────────────────────────────────────────┘█
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Field Names 21
───────────
Compared with dBase, PDT and the programs in the PDT Tool Kit
are more flexible and tolerant regarding field names.
* We won't let you enter blank field names.
* But if you enter a name with spaces (eg., First Name),
we'll just close it up for you when we save it to a dBase
file -- since dBase won't accept blanks.
Please try to closely follow dBase's field name conventions:
* Field names may be 1-10 characters in length.
* They MUST start with a letter (A-Z).
* You may use A-Z, 0-9 and the underscore -- ONLY. Note
you may not included spaces, punctuation, or high or
low ASCII characters.
* They're ALWAYS stored in upper case. In your definition
files you can use any combination of upper and lower case.
But you might want to use upper case to see how recognizable
they'll be in that form.
22
───────────────────────────────────────────────────────────────
SECTION IV: Summary and Explanation of Error Message
───────────────────────────────────────────────────────────────
We've mentioned before that the programs in the Tool Kit WILL:
* Try to prevent you from entering blank field names or
illegal values for field Type or Number of Decimal Places.
* Alert you if they find illegal field names (such as ones
with characters other than A-Z, 0-9 and the underscore.
(Field names MUST start with a letter.)
* Alert you if they find duplicate field names.
In the latter two cases, we'll point out the error and the line
on which it occurred. You can then fix the error and save your
file again.
For other errors, depending on what you're doing, we may be
able to recover and let you fix the error, or we may exit to
DOS. There are 3 general categories of errors: DOS, dBase
File Errors, and Memory or Expression errors.
DOS Errors # Description
────────── ─── ─────────────────────────────────────────────
1 Invalid function number (unlikely)
2 File not found
3 Path not found (invalid drive or directory)
4 Too many files open (increase FILES = )
5 Access denied (Locked file; write protected disk)
15 Invalid drive specified
18 No more files of this type
19 Disk write protected
20 Unknown unit/device
21 Drive not ready
23 Data error (could mean corrupted data)
25 Seek error
26 Unknown media type
27 Sector not found (could mean damaged disk)
29 Write fault ( " " " " )
30 Read fault ( " " " " )
31 General failure ( " " " " )
80 File already exists
DBASE Errors # Description 23
──────────── ─── ─────────────────────────────────────────────
100 Internal error
101 " "
102 Error in file name
103 Erroneous file type
104 Invalid file handle (internal error)
105 File not in state to perform requested action
106 Field Name error
107 Nor fields have been defined
108 Too many fields were defined
109 Field name already defined (duplicate name)
110 Error in field length
111 Too many decimal places
112 Total record length too large for file type
113 Wrong record number or sector address
114 Wrong record string length
115 File is not a valid .DBF file
116 Field number is not valid for file type
117 Wrong value requested for file mode
118 Internal error -- bad buffer
119 Field not found in dBase file
120 File is not a valid .NDX file
121 Key expression is too long
122 Key not found in index
123 End of index encountered (key not found)
124 Duplicate keys not allowed
125 Key or Key Length is too long or too short
Memory/
Expression
Errors # Description
───────────── ─── ─────────────────────────────────────────────
126 Insufficient (out of) memory
127- Memory errors
130
143- Memory errors
147
131- Errors in expressions
140
141 Divide overflow
142 Illegal function or empty string
148 Invalid date argument
149 Invalid date format
24
───────────────────────────────────────────────────────────────
SECTION V: Using FIX-DBF Structure Files.
Exploring or Repairing dBase files.
───────────────────────────────────────────────────────────────
Fix_DBF.Hdr and Fix_DBF.Fld are PDT structure files that can
prove invaluable if you ever need to repair or simply examine
dBase files. You can use these to explore ANY dbase file.
Even if you never use these files, this section can give you
valuable insights into how dBase files are set up.
This section is sent to PDT's registered users.
25
══════════════════════════════════════════════════════════════
APPENDIX I: Other Programs by Pro~Formance
Here's a summary of many of our other programs.
══════════════════════════════════════════════════════════════
══════════════════════════════════════════════════════════════
Professional Scribe (Pro~Scribe) PS Express (PSE)
══════════════════════════════════════════════════════════════
Pro~Scribe and PSE help you improve anything you write (or help
you improve the writing of others -- your staff, students, etc.)
Pro~Scribe is used around the world in companies like IBM,
Hewlett Packard, AT&T, Lockheed, Citicorp and Bank of America to
help improve memos, letters, manuals, documentation, contracts,
promotional material, etc. Here's how Pro~Scribe and PSE help:
* They examine your writing for many types of writing mistakes.
* You can look at overall results for an entire letter,
report, etc. Or, if you like, they'll look at your
writing line-by-line.
* They show suspect problems, and offer suggestions.
* Results are shown numerically, and with colorful graphs.
* They come with two manuals (plus a Quick Reference Guide)
- One covers basics: To install/run PS, and basic guidelines.
- "Effective, High-Impact Writing" has more writing tips.
* They're colorful, fast, fun, and a terrific value:
$39 for both!
How are Pro~Scribe and PSE different? First, PS Express is a
RAM-resident program. That means it's always ready to help
when you need help most--while you're actually writing. Run
PSE, then run your word processor and start writing. Need
help? Just press a key.
* When PSE pops up, just mark the text you want PSE to examine.
A window pops up instantly with feedback on your writing.
* PSE is like having an English teacher looking over your
shoulder, gently coaching you as you write.
Pro~Scribe gives you everything PSE does, and much, much more.
It reads files saved by your word processor, or you can type
text directly into PS. Like PSE, Pro~Scribe shows how complex
your writing, words and sentences are. It also offers you:
* Feedback on "Word Wasters" (5 categories of writing errors).
* Three RGL (Running Grade Level) options (line-by-line feedback).
* An option to flag complex words and Word Wasters in each line.
* A Personal Interest score showing if you write as you speak.
* Options to: Customize the program, send results to your printer.
26
══════════════════════════════════════════════════════════════
Multi-Print The ultimate text printing utility!
══════════════════════════════════════════════════════════════
Multi-Print (MP) prints ASCII text files (like this manual) on
HP LaserJets -OR- Epson -OR- Toshiba printers (or compatibles).
* Print 1, 2 or 4 PAGES of text on each SHEET of paper. Print
in portrait mode on BOTH sides of the paper on ANY printer,
Or print sideways on LaserJets, Epson or Toshiba printers.
- Choose "Booklet" mode to print books. Print the "front"
side, then the "back." Then just fold it into a booklet
and staple!
- Choose "Left-to-Right" to print pages side-by-side, first
on the left side of the page, then on the right.
- Choose "1 Column" per sheet to print up to 250 characters
per line (this is great for printing spreadsheets).
- And with the last 2 options, you can choose to print 2-sided
or 1-sided. Then use them as-is, or slip them into a 3-ring
binder. (Booklets are always printed 2-sided).
* Four fonts are included.
- Our 9-point Times Roman font is a better-looking substi-
tute for the LaserJet's "Line Printer" font (though you
can use the Line Printer font if you wish). With our 6-
point Roman font, print up to 250 characters/line and 80
lines/page (eg., spreadsheets).
- Other fonts let MP print "sideways" on Epson and Toshiba
printers.
* The four fonts contain almost all ASCII characters. Print:
- Lines, boxes, shading, Big! Fonts (tm).
- French, German, Spanish and other language characters.
- "Control codes" (with ASCII values below 32) which are
useful when you want to add arrows, "bullets," "check
boxes" and other symbols to your text.
- NOTE: Original LaserJets and LaserJet + can't print the last 2.
* MP offers many printing options:
- Print TITLES: page numbers, the date, and the name of the
file you're printing (or a "custom title") - in any com-
bination. Print titles at the TOP or BOTTOM of each page
in several "styles."
- Print "both" sides, or just the "front" or "back" side.
- Control Top, Left and Right Margins. "Wrap" long lines of
text (LaserJets only). Print to LPT1, 2 or 3 or "to a
file." Etc.
* MP is menu-driven; choose options using a mouse or the keyboard.
27
══════════════════════════════════════════════════════════════
inform-Z (also see Mail Call below) Professional Forms Design
══════════════════════════════════════════════════════════════
inform-Z is a complete form system. Built-in features include:
easy form design, math, "auto-edit," high quality printing, etc.
Design, edit and print forms with inform-Z.
* Draw lines or boxes, or add shading, in several styles.
* Enter text, auto-centered inside boxes if you like.
* Automatically date, sequence number and time-stamp forms.
* Add "formulas" for spreadsheet convenience, speed & accuracy.
* Quick, easy block options: Copy, Move, Erase, Shading.
* Vary fonts, type styles, line spacing.
* inform-Z is very easy to use. And it's "lesson forms" cut
the learning time dramatically.
Then use inform-Z or Mail Call to fill out forms.
* "Auto-Edit" fields lets you quickly skip through a form,
editing just fields you "marked." On order forms, for
example: Quantity, Description, Price per Unit. Math
options will do the math for you!
* Let Mail Call fill in other information for you -- pulling
names, addresses, etc. from your database, putting them
where you want them.
Produce high-quality, professional looking forms in minutes
with Epson printers or HP LaserJets (+/500/Series II or later).
And you DON'T need expensive font cartridges or soft fonts for
lines, boxes, shading, etc. We use built-in features for
these. "But, I don't have a LaserJet or an Epson" you say.
Not to worry. inform-Z has two other printer options so it
works with any printer.
Together, inform-Z and Mail Call can help you manage almost
every piece of paper in your office.
Forms: Invoices, Purchase Orders, Personnel Forms, Work
Orders, Work Schedules, Travel or Expense Reports,
Accounting Forms, Application Blanks, Org. Charts
As Well As: Letters, Memos, Envelopes, Mailing Labels,
Personalized Documents (ie., form letters),
Reports, Client or Employee lists, etc.
28
══════════════════════════════════════════════════════════════
Mail Call and MC Express (MCE) Our mailing assistant
══════════════════════════════════════════════════════════════
Mail Call (MC) is a full featured mailing assistant. Add names
to a database, then Browse, Search, Print, Sort, etc.
* Print envelopes in several sizes.
* Print mailing labels (several sizes plus a "roll-your-own-
size" option) 1 to 99 copies of each label, 1 to 3 columns
across.
* Print personalized documents (or form letters).
* Print forms -- with "auto-edit," date, sequence number and
math features!
* Print reports, phone books, appointment schedules, etc.
Mail Call offers UNlimited capacity -- use as many database
files as you want. And its "Mail Merge" option lets you
Import or Export names to files used by word processors or
other database programs.
MC Express, a "RAM-resident" program, that lets you: 1) print
envelopes while INSIDE your word processor; and, 2) lets you
"write out" names & addresses to a file you can later "import"
into MC (no re- typing). MCE, optional, works with ALL
versions of the HP LaserJet.
29
══════════════════════════════════════════════════════════════
P~F Presents (PFP) A DESKTOP PRESENTATION System
══════════════════════════════════════════════════════════════
P~F Presents comes with several programs to help you create,
manage and display presentations. The two main programs are
P-Screen and PFP.
With P-Screen you: (See below for more on P-Screen)
──────────────────
* Design screens (or "slides").
* Save screens in libraries (or print them, or save them to
ASCII files, or executable ".COM" files.)
* NOTE: We offer TWO "screen-capture" programs to help you
capture screens from existing applications. One captures
text screens. The other captures ANY type of screen!
With PFP you:
─────────────
* Create presentation agendas ("slide shows") which can include:
- Menus which "branch" to various parts of your presentation,
depending on the option your viewer selects. For example:
-- Which product do you want information on?
-- Which topic (in a tutorial) do you want to review?
- Timed slides (PFP pauses, then automatically shows the next)
- Special effects: animation, sound, loops, exploding windows
* Display your presentations, or let others do it by them-
selves. A "use monochrome" option lets you display presen-
tations on virtually any monitor.
The Possibilities are Endless:
──────────────────────────────
* Sales presentations * Management/Staff briefings
* Training programs * Tutorials or Demos
* Meetings * Highlight product information
* Investment opportunities * Advertising on disk (SoftAds)
* Customer information * Tourist guides
* Restaurant guides * Directories (Names, phone #s)
And on and on and . . .
30
══════════════════════════════════════════════════════════════
P-Screen & P-Screen Professional QuickBASIC screen support
══════════════════════════════════════════════════════════════
P-Screen is a screen: "design," "library/database" and
"display" system all in one. Use it to design screens for
programs you write, or for program demos, prototyping, word
processing, batch files, etc.
* Draw/Join lines or boxes in several styles.
* Shade or Paint entire screens or selected areas.
* Enter text, auto-centered inside lines or boxes if you like.
* Quick, easy block options: Copy, Move, Erase, Shade, Paint,
UnDo.
Save/Load/Libraries
* Save screens to or Load screens from ASCII files or Libraries.
You can also save executable "Com" screens -- colors and all!
- We include a program to "grab" screens from other applications.
* Libraries give you 1-file convenience of storing up to 100
screens -- in color, complete with names and descriptions.
Using screen libraries in your programs, demos, etc.
* We supply routines to display your screens from QuickBASIC
programs (QB 3-4.x or PDS 7.x).
* It's easy to write programs to access screen libraries.
- You can load and display 1 screen at a time.
- Or load 2 or more screens into arrays, then pop them up
instantly.
P-Screen Professional even writes your QB programs for you!!
And it comes with several other subprograms you can use in any
program. Call for **significant** details.
31
══════════════════════════════════════════════════════════════
The Survey Catalyst (A commercial program, not Shareware)
══════════════════════════════════════════════════════════════
The Survey Catalyst (TSC) is for anyone who works with attitude
or opinion surveys. It helps you create surveys in minutes or
hours -- not days!
* TSC includes a database of thousands of survey items--like
items used in most Fortune 1000 companies' employee surveys.
- You can review items, edit them or add new ones.
- OR, when you see an item you want to add to a survey, just
press a key and add it--fast and simple.
* TSC also comes with dozens of response scales. When you print
surveys, TSC prints the right response scale--automatically.
* And speaking of printing, TSC's many options let you create
"camera-ready" copy--as you want it, fast!
- Group items by Category, by Response Scale, or Randomize them.
- Print response scales Above or Beside items (or not at all).
- Print key punch instructions (optional)
- Print a title--at the top or bottom of each page.
- Or, print your survey "to a file"--to dress it up later.
══════════════════════════════════════════════════════════════
Pro~Stamp Stamp Collection Manager
══════════════════════════════════════════════════════════════
Pro~Stamp is our full-featured stamp collection manager.
* It's very easy to use: pull-down menus, extensive on-line
help; Calculations done for you, select "Type" & "Condition"
from menus, and more.
* Your worksheets are set up like most popular collectors'
manuals (eg., Scott).
* Track small to huge stamp collections, with ease and convenience.
* Multiple file options add flexibility (subsets of collections)
* Automatic calculations (Values of each stamp, Increase in
value) give you spreadsheet convenience.
* Sort: On any of several fields.
* Print: Entire worksheets or a range you specify.
* It's customizable: Edit menu items or printer codes your way.
32
══════════════════════════════════════════════════════════════
Ram-Man RAM-resident file browser
══════════════════════════════════════════════════════════════
Ram-Man is a RAM-resident (TSR) program to turn ANY text file
into a pop-up quick-reference guide (or manual). For example,
keep THIS MANUAL at your fingertips while learning inform-Z!
* Pop up your text file while you're working in virtually any
text-based (not graphics) program (including inform-Z).
* BROWSE through it.
* SEARCH, looking for a topic or phrase you're interested in.
* LOOK UP words, which we'll read directly from your screen!
We supply the RAM-resident "engine," you supply the text. Ram-
Man preserves DOS memory by keeping ONLY its engine in memory.
It displays your text from disk (hard or RAM disk recommended).
You can change which file you're viewing without unloading
Ram-Man. That means you load Ram-Man once, then change ref-
erence guides as your needs or the programs you use change.
Now, regardless of which text-based program you're using (or
even at the DOS prompt), you can have on-line, pop-up help
available -- at any time, at the press of a key.
Examples:
* The complete, on-disk manual for a program you're using.
* A series of help screens or "Quick Reference Guides"
(eg., tips on using DOS, tips on using a program).
- You can display standard DOS text files, like those
you create using an editor or word processor.
- Or you can display special "screens" you create with
programs like our P-Screen Screen Designer.
* Appointment Calendars, To Do Lists. . . . etc.
Other features: (<R> = REGISTERED versions.)
* BROWSE through files -- line by line or page by page. And
you can jump to the top or bottom of small -or- huge text
files in 1/2 second or less.
* SEARCH for topics relevant to your needs.
* <R> "LOOK UP" reads a word directly off your screen THEN
searches for it! BE SURE to read the section on Look Up for
uses (eg., Quick reference, spelling, thesaurus, quotations).
* UNLOAD Ram-Man and reclaim the memory it uses.
* <R> RUN-TIME OPTIONS let you choose:
- The "hotkey" you want to use to call Ram-Man up.
- The size of the screen you want to use -- to let you
switch between 25, 43 or 50 row screens at will.
- The colors we use to display text.
These options help ensure that Ram-Man's hotkey, colors
and screen modes never conflict with the programs you use.